<?xml version="1.0" encoding="utf-8"?>
<Content xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:blueonionsoftware-com:bloget:runtime:data">
  <text>From the good folks at &lt;a href="http://thelinuxbox.org/index.php?subaction=showfull&amp;id=1104676550&amp;archive=&amp;start_from=&amp;ucat=3&amp;"&gt;The Linux Box&lt;/a&gt; comes this tip to make Firefox faster. I tried it and it does seem to make a difference: -- mike

&lt;blockquote&gt;After you get past the beginner stage with Firefox, try this "power-user" trick to make it download pages faster by allowing multiple connections so it can download more than one file at a time. It's only useful for broadband users, so if you're still on dial-up you can just skip this one for now.

I came across &lt;a href="http://www.freerepublic.com/focus/f-news/1299854/posts"&gt;this link&lt;/a&gt; tonight, and it's good stuff. After applying these items, I noticed a huge improvement of the speed which Firefox loads pages.

    How To Speed Up Firefox (Helpful Vanity)

    Posted on 12/12/2004 12:45:50 PM PST by KoRn

    Here's something for broadband people that will really speed Firefox up:

    1.Type "about:config" into the address bar and hit return. Scroll down and look for the following entries:

    network.http.pipelining network.http.proxy.pipelining network.http.pipelining.maxrequests

    Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.

    2. Alter the entries as follows:

    Set "network.http.pipelining" to "true"

    Set "network.http.proxy.pipelining" to "true"

    Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

    3. Lastly right-click anywhere and select New-&gt; Integer. Name it "nglayout.initialpaint.delay" and set its value to "0". This value is the amount of time the browser waits before it acts on information it receives.

    If you're using a broadband connection you'll load pages MUCH faster now! 

I would like to state that the network.http.pipelining.maxrequests number of 30 is just an example. The number that may help you best attain your sweet spot will vary based on the speed of your connection. To large a number may cause perceived latency. Also there was some concern over this increasing server loads, but this should not be a problem usually (1 page served is still 1 page served). The exception is if people have frequent disconnects from your site, then the process of pipelining everything simultaneously can be a little more costly.
&lt;/blockquote&gt;
</text>
  <last_update>2007-10-04T00:52:25.2130806Z</last_update>
  <source_title />
  <source_link />
  <comments />
  <references />
  <attachments />
</Content>